Method and system to efficiently manage network connection to connect a client and a resource

ABSTRACT

A method and system to efficiently allocate connections between computer systems in a network are provided. The method and system include determining the type of connections, namely static and dynamic, to be provided for a system. The method and system further include the capability of redirecting a network connection request to a backup resource in the event that the primary resource is unable to serve the request.

FIELD OF THE INVENTION

One embodiment relates generally to the technical field of computer networks, and to methods and systems to efficiently manage connection that is utilized to connect computer systems.

BACKGROUND

Computer networks have become a critical transport mechanism for applications that are becoming increasingly diverse and demanding. With the demand for state-of-the-art applications, guaranteed performance has become a desirable feature of computer network. The computer network should posses a high level of sophistication so as to meet the heterogeneous nature of modern applications. In particular, there is a need for efficient management of connections that are for connecting computer systems in a network.

One method for managing connections is by static connection, as illustrated in FIG. 1. It comprises a dedicated point-to-point connection between the computer systems. The static connection remains established until it is removed by configuration changes. To establish complete connectivity in a network, a connection must be configured and maintained from each node to every other node. This process can become labor intensive and expensive as the number of connections grows rapidly with the addition of nodes. It is also not fault tolerant as each static connection between the nodes is dedicated and is a single point of failure. However, static connections have the advantage of incurring relatively little communication processing cost as they remain established until removed by configuration changes. In addition, as a static connection is a dedicated link, the availability of the connection remains true at all times.

The alternate method is by a dynamic connection, as illustrated in FIG. 2. Contrary to a static connection, a dynamic connection is only established between computer systems when the nodes request a communication session. The connection is terminated once the session is completed. Dynamic connections are shared among the nodes, and therefore, are able to adapt to a growing network. The sharing of connections also enables the network to be fault tolerant. However, there is a need to re-establish the connection for each session and this incurs a processing cost.

A hybrid model, as shown in FIG. 3 and 4, comprises using static connection for connecting some of the computer systems in the network, while the others uses only dynamic connection. Such a network design does not address the problems fully but rather, inherits both the advantages and disadvantages of the static and the dynamic connection.

SUMMARY OF THE INVENTION

A method and system are disclosed for allocating a connection to connect a client and a resource in a network. In one exemplary embodiment, the method and system determine the connection type associated with the connection and establish the connection. The connection type is one of a static connection and a dynamic connection. The determination of the connection type is based on a maximum number of static connections reserved for the client. In another exemplary embodiment, the method and system further include identifying the availability of a backup resource by performing a look-up in a resource table.

Other aspects of the invention will become apparent from the following detailed description in combination with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

FIG. 1 is a network diagram of a prior art approach to connecting a client and a resource by static connections;

FIG. 2 is a network diagram of a prior art approach to connecting a client and a resource by dynamic connections;

FIG. 3 is a network diagram of a prior art approach to connecting a client and a resource by a hybrid model of static and dynamic connections;

FIG. 4 is a network diagram of a prior art approach to connecting a client and a resource by a hybrid model of static and dynamic connections;

FIG. 5 is a block diagram of an exemplary embodiment of the present invention;

FIG. 6 is a network diagram of an exemplary environment in which the invention may be practiced;

FIG. 7 is a network diagram of an embodiment that provides static and dynamic connections according to one embodiment of the present invention;

FIG. 8 is a network diagram of an exemplary embodiment to connect clients to multiple resources;

FIG. 9 is a network diagram of an exemplary embodiment of a network design wherein an embodiment of the present invention may be practiced with some degree of fault tolerance;

FIG. 10 is a flow chart that illustrates one embodiment of a process for establishing static and dynamic connections between computer systems over a network according to one embodiment of the present invention;

FIG. 11 is a flow chart that illustrates one embodiment of a process for establishing static and dynamic connections between computer systems with fault tolerance feature.

DETAILED DESCRIPTION OF THE INVENTION

A method and system to allocate connections between computer systems in a network are disclosed herein. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of the specific details.

As will be described in greater detail below, an embodiment of the present invention provides for establishing connections over a network between computer systems, such as a client and a resource. Advantageously, an embodiment of the present invention is able to determine the type of connection, namely static and dynamic, to be provided for a system. The assignment of the static and dynamic connections may be dynamically changed, based on the demand for the connections and the characteristics of the network. The characteristics of the network include, but are not limited to, the availability, accessibility and load performance of network paths, communication entities and destination systems.

In one embodiment of the present invention, a static connection is first assigned to a client if it is available. Utilizing a static connection may improve the overall efficiency of the network as it does not require connections to be reestablished and, therefore, may reduce the processing time. In addition, the present invention computes the maximum number of static connections reserved for each client based on the demand for the connections. Hence, even if a static connection is available, the client may be assigned a dynamic connection rather than a static connection if it has already depleted its static connections reserve. This seeks to provide a fair assignment of static connections for each client.

In another exemplary embodiment, the present invention includes the capability of redirecting a network connection request to a backup resource in the event that the primary resource is unable to serve the request.

In one embodiment, the operations described herein may be embodied, at least partially, in machine-executable instructions. The instructions can be used to cause a general-purpose or special-purpose processor, which is programmed with the instructions, to perform the operations of the present invention. Alternatively, the operations described herein may be performed by specific hardware components that contain hardwired logic for performing the operations, or by any combination of programmed computer components and custom hardware components.

An embodiment may be provided as a machine-readable computer medium having stored thereon a computer program comprising instructions that may be used to program a computer (or other electronic devices) to perform a process according to the present invention. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, i.e. magnet or optical cards, or other types of media/machine-readable media suitable for storing electronic instructions. Moreover, an embodiment may also be downloaded as a computer program product, wherein the program may be transferred from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by way of data signals embodied in a carrier wave or other propagation medium via a communication link (e.g., a modem or network connection).

Importantly, while embodiments of the present invention will be described with respect to a networking environment, the method and system described herein are equally relevant to other electronic and computing environments in which connections are assigned. For example, it is envisioned that the present invention could be implemented in a multi-processor computing system.

Connection Manager Overview

FIGS. 5, 6 and the discussion herein are intended to provide a description of an exemplary approach to determining a connection for a client. Various embodiments provide different methodologies for manipulating the network data elements and the relationships among the various systems to derive connections for connecting a client to a resource.

FIG. 5 illustrates an exemplary embodiment 200 of a connection manager, further illustrating embodiments of elements 201-204. The connection manager 200 is comprised of a connection management module 201, a connection module 202, a resource table 203 and storage 204.

The connection management module 201 functions to determine the availability of connections and the connection types. It computes the number of static connections reserved for the client based on the number of connection requests and the status of the network. The computation may be performed on real-time data or historical data.

In one example, the connection management module 201 obtains the network information by polling the network system. Alternatively, the connection management module 201 receives the network information broadcasted by the systems in the network.

In addition, the connection management module 201 is able to redirect a connection request to a backup resource in the event that the primary resource is unavailable. The connection management module 201 may perform a look-up in the resource table 203 to determine if a backup resource is available. Similarly, when a primary resource is overloaded, the connection management module 201 may redirect the connection request to a backup resource.

The connection module 202 is responsible for opening a static connection or a dynamic connection with the resource. The connection manager 200 also includes storage for storing the resource table 203, queue information and network process information.

FIG. 6 is a network diagram of an exemplary environment in which an embodiment of the present invention may be practiced. In this embodiment, elements 201-204 of the connection manager 200 reside on different machines or at different physical locations in the network. It will be appreciated by one skilled in the art that elements 201-204 may also reside on different virtual locations.

The connection manager 200 is able to replace elements 202-204 with other resources in the network that accomplish the same function. In one example, if there exists a resource table that contains information of backup resources, the connection manager 200 is able to perform lookup on this resource table instead of its own table 203. In another example, a client may have the capability to open a connection directly with the resource. Therefore, connection manager 200 may inform the client of the type of connection assigned and the client opens a connection directly with the resource. The connection module 202 is not required in this case.

Network Architecture Overview

It is to be understood that the network configurations and interconnections shown in FIGS. 7-9 and described herein, are provided for purpose of illustration only. One of ordinary skill in the art will readily appreciate that the present invention may be practiced on networks more or less complex than that shown, in accordance with the teachings contained herein.

Illustrated in FIG. 7 are a connection manager 200, a resource 300, client computers 400, 410, static connections 510 and dynamic connections 520. In an embodiment, the clients computers 400 and 410 communicate with the resource 300, which is a server computer (or a plurality of computers).

A client computer 400 may comprise a standard computer platform or a specialized computer platform, including, but not limited to a desktop computer, a laptop computer, personal data assistant, and a handheld computer. A number of client computers 400 may be supported by the invention. In an embodiment, the client computers 400 may each comprise a processor, memory, storage devices, a network interface, and a display, which are electrically coupled via buses. A network interface is connected to a communication network (e.g., one or more networks, including, but not limited to the Internet, private or public telephone, cellular, wireless, satellite, cable, local area, metropolitan area and/or wide area networks). Additionally, a client computer, communication network, and server computer could be implemented in a single computer platform, with the communication network being an internal information sharing mechanism such as message passing or shared memory.

The resource 300 is, in the exemplary embodiment, a server computer which may comprise one or more standard computer platforms or specialized computer platforms (e.g., a computer platform optimized for retrieving information and sending information to clients), including, but not limited to one or more desktop computers, servers, mainframes, laptop computers, handheld computers, and personal data assistants. For simplicity, only one server computer is depicted. However, a number of server computers may be utilized. When the invention is used in conjunction with a wide geographic area such as over the Internet, typically numerous client computers and numerous serving computers are used. When a plurality of serving computers are used, they can be co-located, or distributed across the communication network.

In another embodiment of the invention, the client computers 400, 410 and the resource 300 are computer equipments, for example, for the purpose of communications.

In FIG. 7, the client computer 400 makes a request to connect to the resource 300. The connection manager 200 processes the request to determine if the resource is able to provide a static connection 510. If the static connections 510 reserved for client 400 are fully utilized, the connection manager 200 assigns a dynamic connection 520 to the client computer 400. In another example, the static connections 510 reserved for client 410 are available, therefore, the client computer 510 is assigned a static connection by the connection manager 200.

FIG. 8 depicts another network setup, according to an embodiment of the present invention. In this embodiment, the connection manager 200 manages the connection requests for the resources 300, 310 and 320, and acts as a centralized connection management system. Resources 300, 310 and 320 are backup systems for each other.

In an example, the network is set up such that the client computer may make a request connection to a generic resource name. The client computer may be unaware of the multiple resources 300, 310 and 320 associated with the generic resource name. When a client computer 400 makes a request for connection, the connection manager 200 determines the number of static connections reserved for the client computer 400 based on the total requests for the pool of resources 300, 310, 320 by other clients, and also the network status. If the network status reflects that resource 300 is overloaded, the connection manager 200 seeks to assign a connection from resources 310 and 320. The connection manager 200 assigns a static connection 510 to the client computer 400, if the static connections reserved for the client 400 are available.

In another example, the network is setup such that the client computer 400 is only aware of the primary resource 300. Backup resources 310 and 320 are invisible to the client. When a client 420 makes a connection request to the resource 300, the connection manager 200 determines the number of static connections reserved for the client 420 based on the total requests for resources 300 by other clients and the network status. If resource 300 is not available, the connection manager 200 performs a look-up in the resource table 203 to determine if backup resources are available. In this case, the resource table 203 identifies backup resources 310 and 320. The connection manager 200 redirects the connection request to resource 310 and determines if a static connection 510 is available. It will be appreciated by one skilled in the art that different methods of allocating the request to a pool of resources may be applied.

FIG. 9 illustrates another network setup according to one embodiment of the present invention. In this exemplary embodiment, the resources comprise routers 300, 310, 320; telecommunication circuits of service provider A 330 and service provider B 340; and a World Wide Web server 350. The connection managers 200, 201 and 200 are dedicated to a single router, while connection manager 230 is a centralized system for routers 330 and 340.

In one example, when client computer 400 wants to access the World Wide Web server 350, it first makes a request to the router 300. The connection manager 200 of router 300 makes a determination as to whether the maximum number of static connections for client computer 400 has been exceeded. If not, a static connection is assigned to the client computer 400. Otherwise, the system will attempt to provide a dynamic connection. In this example, both static and dynamic connections are unavailable for client computer 400. The connection manager 200 performs a lookup in the resource table to verify the existence of a backup resource. If the backup resource, router 310, is available, the connection request is subsequently forwarded to the router 310. Similarly, the connection manager 210 of router 310 performs the same function of determining the type of connections to be assigned. In this case, a static connection is established between the client computer 400 and router 310.

Next, the router 310 makes a request to establish a connection with a service provider. The configuration in this example is such that the service provider A 330 and B 340 are transparent to the router 310. The router 310 makes a request to a generic resource name, which is associated with service provider A 330 and B 340. The connection manager 230 is a centralized management module for the service providers. It determines the maximum number of static connections reserved for the router 310 based on the total requests for the service providers by other routers 330 and 320, and the network status. A static connection from service provider B 340 is assigned to the router 310.

The next level of communication is between the service provider B 340 and the World Wide Web server 350. Similarly, the connection manager 250 determines the type of connections to be assigned to the World Wide Web server 350.

Connection Types Determination

FIGS. 10 and 11 illustrate the flow diagrams describing an operation to determine a connection type for connecting a client to a resource, according to an embodiment of the present invention. The illustrative embodiment provides for variations and different flow diagrams and methodologies to be used in various embodiments to conform to design decisions in implementing the invention. Moreover, the illustrative embodiment could be embodied in any combination of software, hardware, firmware, etc. Furthermore, the illustrative embodiment provides for programming the functionality required for practicing the invention using any programming technology, paradigm, and/or language that exist today or may be developed in the future, including, but not limited to parallel programming, object-oriented technology, distributed processing, multi-processing, Java, C, C++, and assembly language.

FIG. 10 is a flow diagram illustrating a routine that may be performed by the connection manager 200 to determine a connection type for a client. The routine begins at operation 600, where the connection manager 200 receives a connection request from the client. It proceeds to operation 601 where the connection manager 200 computes the maximum number of static connections reserved for the client. If a static connection reserved for the client is still available, the connection manager 200 opens the static connection at operation 603, and establishes the connection at operation 605. However, if the static connections reserved for the client is fully utilized, it proceeds to operation 604 where a dynamic connection is opened and connected at operation 605.

FIG. 11 is a flow diagram illustrating a routine that may be performed by the connection manager 200 to determine the connection for connecting a client and a resource, in accordance to another exemplary embodiment of the present invention. This routine includes the capability to connect to the backup resources when required. The routine begins at operation 700, and proceeds to operation 701 to determine if the resource is available. If the resource is available, it continues to operation 702 where computation of the maximum static connections reserved for the client takes place. At operation 703, if a static connection reserved for the client is available, it proceeds to operation 704 where a static connection is opened. Otherwise, it proceeds to operation 705 to open a dynamic connection. At operation 706, the connection is then established. However, if at operation 701, a resource is detected to be unavailable, the next operation 707 consists of looking up a resource table to determine the availability of a secondary or backup resource. In operation 708, if the secondary or backup resource is determined to be available, the connection request is redirected to the secondary or backup resource at operation 709. Finally, if the secondary or backup resource is unavailable, the failure to connect is processed at operation 710.

In view of the many possible embodiments to which the principles of the current invention may be applied, it will be appreciated that the embodiments and aspects thereof described herein with respect to the drawings/figures are only illustrative and should not be taken as limiting the scope of the invention. To the contrary, the invention as described herein contemplates all such embodiments as may come within the scope of the following claims and equivalents thereof. 

1. A method for allocating a connection to connect a client and a resource in a network, the method including: determining a connection type associated with the connection; and establishing the connection, wherein the connection type is at least one of a static connection type and a dynamic connection type.
 2. The method of claim 1, wherein the determining of the connection type associated with the connection further includes computing a maximum number of static connections reserved for the client.
 3. The method of claim 2, including determining whether the maximum number of static connections reserved for the client is exceeded.
 4. The method of claim 3, wherein the establishing of the connection further includes opening a static connection, in response to the determination that the maximum number of static connections reserved for the client is not exceeded.
 5. The method of claim 3, wherein the establishing of the connection further includes opening a dynamic connection, in response to the determination that the maximum number of static connections reserved for the client is exceeded.
 6. The method of claim 1, including, responsive to a failure of the resource, performing a look-up in a resource table to determine whether a second resource is available and requesting the connection with the second resource, wherein the second resource is the backup resource.
 7. The method of claim 1, wherein the connection is one of a plurality of connections.
 8. A system for allocating a connection to connect a client and a resource in a network, the system including: means for determining whether the connection is available; and means for establishing the connection, wherein the connection type is at least one of a static connection type and a dynamic connection type.
 9. The system of claim 8, wherein the means for determining whether the connection is available includes means for computing a maximum number of static connections reserved for the client.
 10. The system of claim 9, further including means for determining whether the maximum number of static connections reserved for the client is exceeded.
 11. The system of claim 10, wherein the means for establishing the connection further includes means for opening a static connection, in response to the determination that the maximum number of static connections reserved for the client is not exceeded.
 12. The system of claim 10, wherein the means for establishing the connection further includes means for allocating a dynamic connection, in response to the determination that the maximum number of static connections reserved for the client is exceeded.
 13. The system of claim 8, further comprising means for performing a look-up in a resource table to determine whether a second resource is available and requesting the connection with the second resource, wherein the second resource is the backup resource.
 14. The system of claim 8, wherein the connection is one of a plurality of connections.
 15. A system for allocating a connection to connect a client and a resource in a network, the system including: a connection management module to determine whether the connection is available; and a connection allocation module to establish the connection, wherein the connection type is at least one of a static connection type and a dynamic connection type.
 16. The system of claim 15, wherein the connection management module is to compute a maximum number of static connections reserved for the client.
 17. The system of claim 16, wherein the connection management module is to determine whether the maximum number of static connections reserved for the client is exceeded.
 18. The system of claim 17, wherein the connection allocation module is to allocate a static connection, in response to the connection management module determining that the maximum number of static connections reserved for the client is not exceeded.
 19. The system of claim 17, wherein the connection allocation module is to allocate a dynamic connection, in response to the connection management module determining that the maximum number of static connections reserved for the client is exceeded.
 20. The system of claim 15, wherein the connection management module is to perform a look-up in a resource table to determine whether a second resource is available and to request for the connection with the second resource, wherein the second resource is the backup resource.
 21. The system of claim 15, wherein the connection is one of a plurality of connections.
 22. A computer-readable medium having computer-executable instructions for allocating a connection to connect a client and a resource in a network, including: determining a connection type associated with the connection; and establishing the connection, wherein the connection type is at least one of a static connection type and a dynamic connection type.
 23. The computer-readable medium of claim 22, wherein determining the connection type associated with the connection further includes computing a maximum number of static connections reserved for the client.
 24. The computer-readable medium of claim 23, including determining whether the maximum number of static connections reserved for the client is exceeded.
 25. The computer-readable medium of claim 24, wherein establishing the connection further includes opening a static connection, in response to the determination that the maximum number of static connections reserved for the client is not exceeded.
 26. The computer-readable medium of claim 24, wherein establishing the connection further includes opening a dynamic connection, in response to the determination that the maximum number of static connections reserved for the client is exceeded.
 27. The computer-readable medium of claim 22, including performing a look-up in a resource table to determine whether a second resource is available and requesting the connection with the second resource, wherein the second resource is the backup resource.
 28. The computer-readable medium of claim 22, wherein the connection is one of a plurality of connections. 